Control mechanisms for mobile devices

ABSTRACT

A control mechanism for a mobile communication device includes a first mode element, a second mode element and a third mode element. Each mode element corresponds to a distinct operational mode associated with a particular function of the mobile communication device. A physical switch mechanism, which has a first physical positional state corresponding to the first mode element, a second physical positional state corresponding to the second mode element, and a third physical positional state corresponding to the third mode element, is movable between each physical positional state to select an operational mode and to enable the mode element corresponding to the selected operational mode.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation-in-part of, and claimspriority to, U.S. patent application Ser. No. 09/977,871, filed Oct. 14,2001, titled “Method and Apparatus for Accessing a Contacts Database andTelephone Services”, which is a continuation-in-part of the U.S. patentapplication Ser. No. 09/668,123, filed Sep. 21, 2000 and entitled“Method and Apparatus for Organizing Addressing Elements”, now U.S. Pat.No. 6,781,575, and a continuation-in-part of the U.S. patent applicationSer. No. 09/374,095, filed Aug. 12, 1999, titled “Mobile Computer SystemDesigned for Wireless Communication Expansion”, now U.S. Pat. No.6,516,202, the contents of each herein-being incorporated by reference.

BACKGROUND

1. Field of the Art

The present invention relates to the field of mobile computer systems,and more particularly, to handheld computer system that includes aconfiguration for a wireless data and voice communications.

2. Description of the Related Art

Handheld information organization and communications devices arebecoming increasingly popular for both business users and more generalusers. For example, handheld systems such as a personal digitalassistant (PDA) offered by Palm, Inc. (Sunnyvale, Calif.) orHewlett-Packard (Palo Alto, Calif.) have found widespread acceptanceamongst people for the purpose of organizing their calendars and storingpersonal contact information. Typically, these PDAs contain PersonalInformation Management (PIM) applications such as an address book, acalendar application, a memo application, and a to-do list application.The popularity of these devices is due in part to their small formfactor and operational readiness (no “boot” time required). Thus, PDAsallow convenient and instant access to a large amount of personalinformation.

Over time, research has indicated that having a simple intuitive methodof quickly accessing the personal information data is a feature ofimportance for many users of a PDA. Operating systems designed aroundthis principle, for example, the Palm Operating System (PalmOS) fromPalm Source, Inc. (Sunnyvale, Calif.), have captured a large proportionof the PDA market. An advantage of such operating systems is theflexibility with which a user can select and manipulate data in a numberof different ways. For example, a user may use up/down scroll buttons,can select an item displayed on a touch screen, and/or scroll throughdifferent category lists by repeatedly pressing an application button.In some contexts, such as an address book application, this allows auser to store and access a list of acquaintances and contact detailsrelatively quickly and efficiently. Nevertheless, there continues to bea need for a new, useful interface that allow a user to select andarrange items in such lists quickly and in a simple manner.

In addition to a PDA, many users also consider a cellular telephone tobe an essential tool. Hence, many users have both a PDA and a cellulartelephone. The PDA provides functionality such as use as PIMorganization. As an example of how a user uses both devices, if a userhas a call scheduled with a contact, the time of that call may be notedin a calendar of the PIM. When the user is ready to initiate the call,the user references the contact's telephone number in the address bookof the PIM and thereafter dials that contact on the cellular telephone.The need to consult and interact with two separate devices isinconvenient as both time-consuming and cumbersome.

One attempt to address these shortcomings was the pdQ Smartphone fromQUALCOMM Incorporated (San Diego, Calif.), which is illustrated in FIG.1A. The pdQ Smartphone includes a display indicator showing telephonemode status. The pdQ Smartphone also includes a closed keypad withpush-buttons for dialing telephone numbers, as well as status lights, aspeaker, and a microphone. FIG. 1B illustrates another view of the pdQSmartphone. In this view, the keypad of the pdQ Smartphone is shown inan opened position exposing an organizer. The organizer includes ascreen, a writing area, and soft buttons.

Although the pdQ Smartphone combines some of the functionality of anorganizer and a cellular telephone, it includes number of drawbacks. Onedrawback is it requires a separate dialing keypad for telephonefunctions and a separate input area for the PDA. This increase deviceform factor and increases device manufacturing costs associated with theseparate dialing keypad. Another drawback is the pdQ Smartphone lacksexternal control functions not directly related to operation of thephone or the PDA portion, but applicable to both. For example, there isno mechanism to control speaker functions when the phone is notoperational.

Yet another drawback is many users have two or more voicemail accounts,e.g., cellular phone, work, and home, which limits operationaleffectiveness of devices such as the pdQ Smartphone because it providesoptions for use with only a single voicemail account. Still anotherdrawback is the pdQ Smartphone allowed access to networks, e.g., theInternet, but only through a dialing option. Devices thereafter haveallowed for access to networks such as the Internet through generalpacket radio service (GPRS) or a wireless network connection, e.g., IEEE802.11, but requires software to control radio operation functions suchas ON and OFF. This can be inconvenient because it requires the user tonavigate through user interface menus or buttons, which may not beintuitive, while also making it a relatively time consuming task.

Therefore, there is a need for an improved apparatus and method forcombining and managing functionality of a handheld computing device anda mobile communication system (e.g., telephone or other networkeddevice).

SUMMARY

The disclosed embodiments also include a handheld computing system,e.g., an organizer, that integrates wireless communications (e.g.,mobile (or cellular)) telephony functionality. The handheld computingsystem is configured to function with the telephony features.

One disclosed embodiment includes a corresponding user interface for anintegrated handheld computer computing and telephone system. By way ofexample, a telephone system user interface is configured to provide afamiliar user interface to the user. In one embodiment, a user ispresented with an option of a predetermined number, e.g., four,available user interface views and yet another user interface view,e.g., a fifth view, that is available when there is an active telephonecall. These views are displayed on a digitizer pad, or example, a“touch” sensitive display (e.g., pressure-sensitive (resistive),electrically-sensitive (capacitance), acoustically-sensitive(SAW—surface acoustic wave) or photo-sensitive (infra-red)) and can beinteracted with through the display itself.

An embodiment of a first user interface view includes a dial pad viewthat is similar to a common touch tone dial pad. However, the dial padview has added functionality and may automatically switch to other viewsas needed. A second available user interface view includes a speed dialview. The speed dial view allows users to easily create their owncustomized speed dial buttons that are easy to navigate between and canbe edited at any time. The system may automatically switch from thespeed dial view in certain circumstances.

A third user interface view includes a call history view. The callhistory view displays a list of previous incoming, outgoing, or missedcalls and may be. filtered as desired. As with the previous two views,the system may automatically switch from the call history view toanother user interface view as necessary. A fourth user interface viewincludes a contacts view. The contacts view provides a filteringmechanism that allows the user to search quickly and intuitively througha large personal contacts database. A fifth user interface view includesthe active call view. The active call view displays a set of commandbuttons for accessing advanced telephone features during a telephonecall such as hold, three-way calling, DTMF touch tones, hang-up,speakerphone, etc.

The disclosed embodiments also include a ‘QWERTY’-type keypad (orkeyboard) that is integrated with the integrated handheld computer andtelephony system. The QWERTY-type keypad includes conventional keypad(or keyboard) keys structured in a QWERTY layout. The keys allow forconventional text and character input for applications running(executed) by the handheld computer portion of the integrated system.However, a portion of the keys can also be apportioned in aconfiguration reminiscent of a telephone dial-pad (e.g., numericalplacement of 1-9 and 0 as well as characters ‘*’ and ‘#”). The keys thatprovide such dual operational functions operate as a dial pad when atelephony application of the integrated computer and telephony system isrunning. In one embodiment, the dual operational function keys includethe ERT keys with also function as 123 when the telephony application isoperational (likewise, DFG correspond to 456 and XCV to 789). In anotherembodiment, YUI can correspond with 123, HJK to 456, and BNM to 789.

The disclosed embodiments provide a fully functional input mechanismthat appropriately corresponds to applications operating in a handheldcomputing configuration or a telephony configuration. This providesusers with a familiar, easy to use interactive input mechanism withoutcomprising functionality of the familiar input mechanism. Moreover, theautomated switch over between user interfaces depending on whether theapplication is handheld computer (e.g., data) related or telephonyrelated further increases ease of use and operation. In addition, otherdisclosed features and embodiments further allow for operationalefficiency and ease of use of the integrated handheld computer andtelephony system. For example, multiple voicemail management, radiotransmission management for data communication, and interfacemanagement.

Further disclosed embodiments include a set of external physical switchmechanisms that beneficially control operational aspects of the handheldcomputer and wireless communication device without having to navigatethrough user interface screens. In one embodiment, the device includesan n-way physical switch, where n is equivalent to a number of desiredmodes of a particular function. The n-way physical switch may be, forexample, a slider, a rocker, a button, or a solid state (e.g., pressuresensitive) type switch. With respect to its modes of operation, if thefunctionality is, for example, notification options, the switch may be a3-position switch in which each position corresponds to a particularnotification mode. By way of example, one notification mode may besilent (e.g., no notification on receipt of a communicative (e.g., phonecall, email or instant message)), one may be sound (e.g., play a ringtone on receipt of a communicative), and one may be vibrate (e.g., nosound, but vibrate the device on receipt of a communicative). Thus,control over how the device will function relative to a surroundings isbeneficially controllable through an easy to use, intuitive physicalcontrol mechanism rather than through user interface softwaremechanisms.

The features and advantages described in the specification are not allinclusive and, in particular, many additional features and advantageswill be apparent to one of ordinary skill in the art in view of thedrawings, specification, and claims. Moreover, it should be noted thatthe language used in the specification has been principally selected forreadability and instructional purposes, and may not have been selectedto delineate or circumscribe the inventive subject matter

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed embodiments have other advantages and features which willbe more readily apparent from the following detailed description and theappended claims, when taken in conjunction with the accompanyingdrawings (or figures), in which:

FIG. 1A illustrates a prior art phone in a closed position.

FIG. 1B illustrates the prior art phone in an open position.

FIG. 2A illustrates one embodiment of a front isometric view a handheldcomputer system on which an embodiment of the present invention may beimplemented.

FIG. 2B illustrates one embodiment of a rear isometric view of thehandheld computer system of FIG. 2A.

FIG. 2C illustrates one embodiment of a front isometric view of thehandheld computer system of FIGS. 2A and 2B equipped with a wirelesscommunications peripheral attachment.

FIG. 3A illustrates one embodiment of a front isometric view of anintegrated stylus-based handheld computer and cellular (or mobile)telephone system.

FIG. 3B illustrates one embodiment of a rear isometric view of anintegrated keyboard-based handheld computer and cellular telephonesystem.

FIG. 3C illustrates one embodiment of a keyboard layout for the handheldcomputer and cellular telephone system of FIGS. 3A and 3B.

FIG. 4 illustrates one embodiment of a block diagram of hardwareelements of a telephony portion of a handheld computer system.

FIGS. 5A through 5C illustrate another embodiment an integrated handheldcomputer and wireless communication device configuration.

FIG. 6 illustrates one embodiment of a block diagram of the softwareelements of the cellular element's system.

FIG. 7 illustrates one embodiment of the screen options of a handheldcomputer system.

FIG. 8A illustrates one embodiment of screen shots for a dialing processfor telephony operation.

FIG. 8B illustrates one embodiment of screen shots as the system isnavigated through an incoming call alert.

FIG. 8C illustrates one embodiment of screen shots for a call history.

FIG. 9A illustrates a flow chart of one embodiment of a process ofadding a voice mailbox to a speed dial system.

FIG. 9B illustrates one embodiment of screen shots for voicemailcontrol.

FIG. 10 illustrates a functional block diagram of a telephone userinterface software application.

FIG. 11A illustrates one embodiment for a display arrangement for atelephone dial pad user interface view.

FIG. 11B illustrates the telephone dial pad user interface view of FIG.10A when there is an active telephone call.

FIG. 12 illustrates one embodiment for a display arrangement for atelephone call history user interface view.

FIG. 13 illustrates one embodiment for a display arrangement for atelephone speed dial user interface view.

FIG. 14 illustrates one embodiment for a display arrangement for atelephone speed dial page editing user interface.

FIG. 15A illustrates one embodiment for a display arrangement for atelephone speed dial record creating user interface.

FIG. 15B illustrates one embodiment for a display arrangement for atelephone speed dial record editing user interface.

FIG. 16 illustrates one embodiment of a series of user interface screensnavigated by a user when creating a new speed dial entry in an emptyspeed dial slot.

FIG. 17 illustrates one embodiment of a series of user interface screensnavigated by a user when creating a new speed dial entry in a speed dialslot that already has a current speed dial record.

FIG. 18 illustrates one embodiment of a series of user interface screensnavigated by a user when editing an existing speed dial entry from adifferent speed dial page.

FIG. 19 illustrates one embodiment for a display arrangement for atelephone contacts user interface view.

FIG. 20 illustrates a first view of one embodiment of a displayarrangement for a telephone active call user interface view.

FIG. 21 illustrates a second view of one embodiment of a displayarrangement for a telephone active call user interface view.

FIG. 22 illustrates one embodiment of an alert screen that may bedisplay when an incoming call is received and the lid of the telephoneis open.

FIG. 23 illustrates one embodiment of an alert screen that may bedisplay when an incoming call is received and the lid of the telephoneis closed.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, specificnomenclature is set forth to provide a thorough understanding of thepresent invention. However, it will be apparent to one skilled in theart that these specific details are not required in order to practicethe present invention. For example, the present invention has beendescribed with reference to handheld computer and wireless communicationsystems, including mobile (or “cellular”) telephone systems. The mobile(or cellular) telephone system includes portable voice-over Internetprotocol (VOIP) devices. Further, the same techniques can easily beapplied to other types of wireless communication devices designed forportability and roaming, e.g., BlackBerry platform devices from Researchin Motion Limited (Canada) or GoodLink from Good Technology, Inc.

Handheld Computer and Wireless Communication Device

FIGS. 2A and 2B illustrate one embodiment of a handheld computer system100. As illustrated in FIG. 2A, the front of the handheld computersystem includes a display area 120 and several physical buttons 130. Thehandheld computer system is structured to fit, and be controller from, apalm of a hand. Example form factors include cordless telephones, mobile(or cellular) telephones, personal digital assistants (PDAs), andpersonal communicators (e.g., a Treo® Smartphone from Palm, Inc.(Sunnyvale, Calif.) or a BlackBerry® phone from Research in MotionLimited (Canada)).

The display area 120 includes a visual display device, such as a liquidcrystal display for presenting information to the user. A user maymanipulate the physical buttons 130 to input information into thehandheld computer system 100 and make selections of informationpresented on the display area 120. In a preferred embodiment, thedisplay area 120 may also be covered with a digitizer pad that can beutilized by the user to enter information to the computer system using,e.g., a stylus (not shown) or a finger. It is noted that the digitizerpad may also be referenced as a “touch” sensitive display (e.g.,pressure-sensitive (resistive), electrically-sensitive (capacitance),acoustically-sensitive (SAW—surface acoustic wave) or photo-sensitive(infra-red)) and can be interacted with accordingly.

In operation of the preferred embodiment, the display area 120 displaysinformation to the user of the handheld computer system 100. The user isthen able to employ, e.g., a stylus, a finger, or inductive pen, tomanipulate and interact with the displayed information by touching thedigitizer pad overlaid on top of the display device. In one mode ofoperation, a stylus can be used in the manner of a writing pen to entercharacters and figures by drawing the stylus across the digitizer pad.

In one embodiment, the user is instructed to enter text into a specificarea 125 of the digitizer pad. The stylus and digitizer may functionlike a computer mouse to operate and manipulate interactive elements onthe display. For example, the computer system may present a virtualbutton in a location on the display that can be activated to perform anassociated function by the user tapping the stylus or a finger on thedigitizer pad at the virtual button location. The stylus can also beused to perform “drag and drop” operations in the fashion known in theuse of a computer mouse.

The handheld computer system 100 also includes an expansion connectorslot 110, seen in a rear view of FIG. 2B. The expansion connector slotallows peripheral devices to be connected to the computer system tointeract therewith. Many kinds of peripheral devices can be connected tothe handheld computer system 100 through the expansion connector slot110 including, GPS receivers, memory modules, pager modules, andcellular telephone transceivers.

FIG. 2C illustrates an isometric view of a handheld computer system 100as described above, with a cellular telephone transceiver 150 coupledthereto by the expansion connector slot 130. The cellular telephonetransceiver 150 comprises a first portion 152 that is fixed to the bodyof the handheld computer system and a second portion 154. The secondportion 154 of the radio telephone device is hingedly coupled to thefirst portion 152 to allow it to pivot from a closed position where itcovers the display area 120 to an open position as shown in FIG. 2C.When in the open position, a speaker 156 in the second portion of thecellular telephone transceiver 150 can be held proximate to the ear ofthe user while the user speaks into a microphone 112 provided in thehandheld computer system 100.

The cellular telephone transceiver 150 includes circuitry for enablingcommunications with a cellular telecommunications network and processingcircuitry that, together with onboard software or firmware, allows thecellular telephone transceiver 150 to interact with the handheldcomputer system 100. Various aspects of a handheld computer system andinterconnected cellular radio telephone are described in U.S. Pat. No.6,516,202 and entitled “A Mobile Computer System Designed for WirelessCommunication Expansion”, which is hereby expressly incorporated byreference in its entirety.

It will be appreciated that the handheld computer system 100 andfunctions of the cellular telephone transceiver 150 operate principallyunder the control of computer software. The handheld computer system 100includes a microprocessor and built-in software that providesapplication programs for the user. The cellular telephone transceiver150 may also include a microprocessor, together with software code anddata specifically required for the telephone functions.

In a preferred embodiment, a computer software phone application thatprovides the user interface functions for the cellular telephonetransceiver peripheral 150 executes on the handheld computer systemmicroprocessor. However, the software code may be permanently stored ineither the handheld computer or the cellular telephone transceiverperipheral 150. Similarly, data used by the phone application can bestored in either device, although it is preferred that acquaintancecontact data and the like be stored in the handheld computer system sothat it may be accessible by the user even when the cellular telephonetransceiver peripheral 150 is coupled to the handheld computer system100.

Integrated Handheld Computer and Wireless Communication Device

To reduce the number of devices that a user needs to carry around, anintegrated handheld computer system and mobile communication (orcellular telephone) system is introduced. FIGS. 3A and 3B illustrate oneembodiment of an integrated handheld computer and cellular telephonesystem 300. The integrated handheld computer and cellular telephonesystem 300 includes a keyboard 330 such that the user may easily enternames, addresses, phone numbers, and email messages into applicationprograms running on the integrated handheld computer and cellulartelephone system 300.

FIG. 3C illustrates one embodiment for the keyboard (or keypad) 330 thatmay be used in the handheld computer and cellular telephone system 300of FIGS. 3A and 3B. The illustrated keyboard 330 is configured in aconventional ‘QWERTY’ layout. The keyboard of FIG. 3C includes an optionkey that is used to generate secondary characters from the various keys.For example, the “E” key 361 normally generates an “E” character. But ifthe “E” key 361 is pressed while simultaneously holding the option key301, then the “$” character will be generated.

The keyboard of FIG. 3C also includes a digit dial pad area 391. Thedigit dial pad area 391 is laid out like a conventional touch-tonetelephone dial pad. In this manner, a user may dial telephone numbersusing the familiar mechanical touch-tone telephone dial pad. Note thatthe digit dial pad area 391 uses the same keys used for various letters.To explicitly generate a number, a user should press the option key 301in order to generate a numerical digit from the keys in the digit dialpad area 391. However, the software in the handheld computer andcellular telephone system 300 may interpret any key press in the digitdial pad area 391 as a numerical digit in certain contexts whether ornot the option key 301 is depressed. For example, if the user isentering a telephone number in a telephone number input field of acontact record, any key press from the digit dial pad area 391 will beinterpreted as a numerical digit whether or not the option key 301 isdepressed.

In an alternate integrated handheld computer and cellular telephoneembodiment (not shown), the alternate integrated handheld computer andcellular telephone system lacks the keyboard 330 of FIG. 3A. In such anembodiment, the user enters text and numerical information using astylus as set forth in the handheld computer system of FIGS. 2A through2C.

Example Data and Wireless Communication Configurations

FIG. 4 illustrates one embodiment of a block diagram of hardware (e.g.,solid state) elements of a wireless communications (e.g., telephonyportion) of a handheld computer system. In one embodiment, the telephonyportion can be a separate physical unit that couples through anexpansion slot 410 is the connection portion 110 of the first embodimentof the handheld computer system 100. In another embodiment, thetelephony portion is integrated with the remainder of the handheldcomputer system, for example as previously illustrated and describedwith respect to FIGS. 3A and 3B. By way of example, the telephonyportion will be described in the context of the separate physical unitwith respect to FIG. 4, although the principles of operation areapplicable for the integrated telephony and handheld computer systemembodiment. The example in FIG. 4 of the handheld computer system 100may also be referenced as a personal digital assistant or organizer.

In FIG. 4, the expansion slot 410 is coupled to the organizer extension420. The organizer extension 420 is hardware which is part of thecellular element, but is under the control of the organizer, and behavesas an extension of the organizer. The organizer extension 420 includesread only memory (ROM) 425, and a bidirectional communication medium.For one embodiment, the bi-directional communication medium is aUniversal Asynchronous Receiver Transmitter (UART) 430. For anotherembodiment, the bidirectional communication medium may be a FIFO,Dual-port, RAM, registers, or other such devices. The ROM 425 includesthe code to install a portion of the software on the organizer to allowthe organizer to interface with the cellular element, and to uninstallthe installed software. For one embodiment, the ROM 425 further includessoftware which is executed in-place by the organizer.

The phone specific hardware 440 is the hardware in the cellular elementthat is used to control specific telephone functionalities. The phonespecific hardware 440 may include: a radio frequency (RF)/antenna 445,an intermediate frequency (IF) logic 450, a power connection 470, acoder/decoder/speaker unit 465, a microcontroller 460, and otherfunctions 455. For one embodiment, the microcontroller 460 includes adigital signal processor (DSP). The microcontroller 460 interfaces withthe organizer, via the organizer extension slot 410 and the UART 430.The microcontroller 460 also controls the functions of the otherelements of the cellular element. The microcontroller 460 sends aninterrupt signal 485 to the organizer when a telephone call is received.For one embodiment, the “telephone call” can include voice, data, or faxconnections.

For one embodiment, the microcontroller 460 also monitors the batterylevel signal 490. If the battery level signal 490 indicates that theorganizer does not have a battery in or if the battery level is below athreshold, the microcontroller 460 does not send the interrupt signal485. Generally, when a call is received, the organizer is asked torespond. Using the battery level signal 490, the organizer is not askedto respond when the battery level is below the threshold. This preventsthe stand-by power from being exhausted, possibly leading to memoryloss.

The codec/speaker 465 receives a microphone signal 495 from theorganizer expansion slot 410. For one embodiment, the microphone signal495 is connected directly through the organizer from a microphone 415 inthe organizer. The organizer itself does not touch the microphone signal495, but merely passes it to the codec/speaker 465. The speaker itselfis in the cellular element. In this way, the microphone 415 in theorganizer is integrated into the codec/speaker 465 in the cellularelement.

The power 470 is a battery or other device configured to maintain powerto the microcontroller 460 and the other elements of the cellularelement. The power 470, for one embodiment, receives a power connection498 from the organizer. The power connection 498 may provide auxiliarypower, operational power, or charging power to the cellular element. Forone embodiment, the power connection 498 is connected through theorganizer expansion slot 410, to an organizer cradle slot. One of theinterconnections between the organizer and the cradle is a powerconnection. This power connection is routed through the organizer,without being used within the organizer, to couple the power signal 498to the power element 470, when the cellular element is coupled to theorganizer. The power connection is used to charge the battery in thecellular element. For one embodiment, the power element 470 may furtherinclude a backup power source, such as a battery or capacitor, tomaintain memory or otherwise maintain necessary data within thephone-specific hardware 440, if the cellular element has not beencharged in some period.

FIGS. 5A through 5C illustrate another embodiment an integrated handheldcomputer and wireless communication device configuration in accordancewith the present invention. The wireless data communication system canbe configured as a separate module for use with an expansion slot of ahandheld computer system as illustrated and described with respect toFIGS. 2 a and 2 b or can be within the integrated data and cellularsystem as illustrated and described with respect to FIGS. 3 a and 3 b.It is also noted that the data communication system can be aconventional wireless data communication system, for example, generalpacket radio service (GPRS), IEEE 802.11b/a/g/n (or WiFi), or IEEE802.16 (or WiMax).

FIG. 5 a illustrates one embodiment of a wireless data communicationsmodule 510. The wireless data communications module 510 includes anantenna 512, a radio 514, and a processing component 516. The processingcomponent 516 includes conventional data processing components such as abaseband processor (PHY) 516 a, a media access control (MAC) layer 516b, and central processor (or controller) unit (CPU) 516 c. The antenna512 is configured to transmit and receive radio frequency signals.Preferably, the antenna 512 is the antenna 445, although in alternativeembodiments is may be a separate antenna. The antenna 512communicatively couples the radio 514. The radio 514 communicativelycouples the processing component 516 and a power management interface.The processing component 516 communicatively couples with the powermanagement interface, a memory interface, a clock (CK), a hostinterface, and a mode interface.

The baseband processor and media access control layer provide aconventional communications intermediary for data communications. Thememory interface and the clock allow the processing component 516 to usethe system memory and clock of the integrated handheld computing andmobile communications (or telephony device), which helps reduce systemcost and size by eliminating duplicative functional components.Nevertheless, in alternative embodiments a separate dedicated memoryand/or clock may be used with the processing component 516. The hostinterface is used for the processing component 516 to communicativelycouple a host processor or controller within the handheld computing andwireless communication device. The mode interface is used for theprocessor component 516 to communicatively couple with one or more modesof operation, for example, as described with respect to FIG. 5B.

The radio 514 and processing component 516 are configured to providedata communications functionality. For example, these modules may beconfigured for WiFi or WiMax communications. Moreover, they can beconfigured to communicatively couple through the host interface thehandheld computing device components, for example, the organizer 420 orany of the other handheld computing applications described herein.

FIG. 5B illustrates one embodiment of a physical switch configuration520 for use with a handheld computing and wireless communication devicein accordance with the present invention. The switch configurationincludes a switching mechanism 522 that is coupled with a power module526. The switch configuration is structured to toggle between one ormore switch contact points 524. In this illustrated example there arethree switch contact points 524 a-c. Attached to each contact point 524is a mode element 528, illustrated in this example as A (528 a), B (528b), and C (528 c). Each functional elements communicatively couples witha processor of the handheld computing and wireless communication device(e.g., processor unit 516 c or microcontroller 460 or other deviceinternal processor or controller), which assists in carrying out theparticular functionality of the mode element 528.

In a preferred embodiment, the function of each mode element 528 isrelated, although each has a distinct characteristic (or mode) relativeto the other mode elements. For example, the functionality may involvenotification. Example modes for notification may be silent (e.g., nonotification) as mode A 528 a, sound (e.g., ring or ring tone) as mode B528 b, and actuation (e.g., vibrate; optionally may include or exclude asound) as mode C 528. The switch mechanism 522 can be physically toggledto select a particular mode 528 a-c. When a particular mode is selected,it is powered through the power module 526. The selected mode module 526thereafter can instruct the processing component 516 to activate theappropriate functionality as selected through the switch mechanism 522.

By way of example, if mode A 528 a is selected the processing component516 can mute the speaker and stop an actuation mechanism within thedevice. If a ring mode 528 b is selected, a ring tone may be retrievedby the processing component 516 from a memory (e.g., retrieve a storedMP3, WMA, or AVI ring tone) to play on a device speaker when sound isreceived. If an actuate mode 528 c is selected, the processing component516 can mute the speaker and trigger an actuation mechanism to operatewhen, for example, a telephone call is received.

In another example embodiment, the functionality may correspond to aselection of a communications operator and the mode function may allowfor selection among the various operators. For example, thecommunication medium may be a connecting the mobile telephone componentwith a mobile telephone network. The modes 528 a-c may correspond with aCDMA network, a GSM network or no network. Thus, device beneficiallyprovides a mechanism to communicatively couple a variety of mobilecommunication networks without having to replace or change hardwarecomponents when a carrier network is changed. It is noted that thisfunctionality may be structured through the software as an alternativeto the described physical switch mechanism configuration.

In this example configuration, each mode element would include thecomponents necessary to function on the appropriate network. It is notedthat the mode elements 528 in this configuration may be physicallyseparated or logically grouped (where components may be shared) once aparticular mode 528 is physically selected through the switch mechanism522. In the logical grouping configuration, the processing component 516or another intelligent mechanism (e.g., a controller) may be configuredto communicatively couple the appropriate communication elements withinthe device, which would correspond to the particular mode ofcommunication selected.

In yet another example embodiment, the switch mechanism 522 and modeelement 528 structures can be configured for data communications. Inthis example, the mode elements 528 may correspond to control over awireless data communications. For example, the modes in thisconfiguration may be radio ON or radio OFF (e.g., placing a WiFi, WiMax,or Bluetooth radio in an ON state may correspond to transmitting orreceiving WiFi, WiMax, or Bluetooth radio signals and placing it in theOFF state may correspond to no transmission or receipt of WiFi, WiMax,or Bluetooth radio signals). Such configurations are particularly usefulin managing personal area networks, e.g., Bluetooth connections, betweentwo or more devices because at least one of the devices can be placed inan ON state or OFF state through a physical switch on the device. Theconfiguration simplifies use and operation because a user has immediateaccess to a control mechanism over the radio state rather than having toturn on a user interface screen and navigate through graphical screenuser interfaces to reach the appropriate screens to exercise controlover the radio state. As with the previous examples, the structuring thedevice to change functionality with physical controls rather thansoftware controls allows for ease of use and greater functional controlover the handheld computer and wireless communication device.

It is noted that when a particular mode is selected through the switchmechanism 522, additional levels of notification may be provided. Forexample, in the notification configuration switching to an actuationmode, e.g., mode C, may actuate (e.g., vibrate) the device. Likewise byway of example, switching to a sound mode, e.g., mode B, may cause abrief ring sound or tone. For other functional switching aspects, asystem and process can be configured to match particular devicefunctionality (e.g., no sound, sound, actuate (with or without sound))with a particular mode. For example, setting if the switching mechanismis directed to WiFi radio ON state and OFF state, an ON state cantrigger a sound or actuate the device briefly with one characteristic(e.g., a sound pattern (such as long and/or short beeps) or a vibrationpattern (short. and/or long vibration duration) and an OFF state maytrigger a sound or actuate the device with another characteristic (e.g.,separate sound or vibration pattern). The additional level ofnotification beneficially provides a user of a device information ofwhich mode is functional without having to visually inspect the switchmechanism, the screen, or other part of the device.

Selection of a mode can be made through a physical contact with acontact point, e.g., 524. Alternatively, the switch mechanism 522 andcontact point 524 configuration can be replaced with functionalequivalent elements of a semiconductor controller device (or the like)with allows for physical toggling of the switch and selection of aparticular mode 528 a-c. Further, the principles of the switchingmechanism may be applied to other devices such as laptops or peripheralcomputing systems to the handheld computer and wireless communicationdevice.

FIG. 5 c illustrates one embodiment of a handheld computer and wirelesscommunication device 530 with two switch areas 532, 534. In this exampleembodiment, one switch area 532 is located across a top of the device530 and the other switch area 534 is located along a side (and regionperpendicular to the top) of the device 530. Each switch area 532, 524corresponds with a separate switch mechanism, e.g., 522, and modeelements, e.g., 528. One switch area can be configured for onefunctional aspect and the other for another functional aspect. Forexample, the first switch area 532 can be structured for notification asdescribed above.

The second switch area 534 can be structured for selection of wirelesscommunication networks, also as described above. It is noted that eachswitch area 532, 534 can be structured as, for example, a slider switch,a rocker switch, a set of buttons, or a solid state switch (e.g.,pressure sensitive switch) or a combination thereof. The switch area532, 534 switches can toggle between n positions, one for each availablemode. For example, if the first switch area 532 corresponds withnotification, the switch may be three-position slider, rocker, or solidstate switch.

FIG. 6 illustrates one embodiment of a block diagram of the softwareelements of a wireless communications (e.g., mobile (or cellular)telephony) system. The software includes program code (instructions)that executes on the handheld computer (e.g., organizer) 610 andsoftware that executes on the cellular element 650. In one embodiment,the software that executes on the handheld computer system may beexecuted in place from the cellular component's memory. In anotherembodiment, the software that executes on the handheld computer systemmay be uploaded to the handheld computer system memory, and executedfrom there.

The software that executes on the handheld computer system includes aphone application 620. The phone app 620 controls the user interface,database, and system level operations of the cellular element. Thesoftware may further be configured to include an address book 625. Inone embodiment, the address book changes format when the cellularelement couples with the organizer. For example, the address bookdisplays a single-key dialing ability when the cellular element couplesthe handheld computer portion (physically, if a separate component, orlogically, if an integrated component).

Other applications 630, such as conference calling, e-mail, web browser,etc. may be part of the software that runs on the handheld computersystem. Any application that is altered by the connection of thecellular element with the handheld computer would be included in thislist. The software that executes on the cellular element 650 interfaceswith the software that executes on the handheld computer using anapplication programming interface (API) 640. For one embodiment, the API640 runs over serial communications, over the bi-directionalcommunications medium.

For one embodiment, the software that executes on the cellular element650 runs on the microcontroller in the cellular element. For oneembodiment, the software that executes on the cellular component 650includes the phone OS 660, cellular telephony protocol stack 670, andhardware control and interface 680. The cellular telephony functionsinclude the cellular protocol stack, frequency/code selection, controlof data services, etc. In one embodiment, functions directly related tomaking a connection to the network are handled in the software thatexecutes on the cellular component 650. Functions for databasemanagement, storing and retrieving information about the connection,etc. are executed on the handheld computer.

Interactive User Interfaces

FIG. 7 illustrates one embodiment of the screen options of a handheldcomputer system. The base views 710 include three screens, the speeddial screen 715, phone pad 720, and dial log 725. The speed dial screen715 permits access to an edit screen 730, on which the user can edit thelist of speed-dialed numbers, an edit entry screen 735 which permitsediting of an existing entry, and a find number screen 740 which permitsa search of existing telephone numbers, in the address book andelsewhere, to add to an entry.

The phone pad 720 includes software generated numbers to dial. The dialstatus screen shows the status of current calls. The dial log screen 725includes a log of past dialed and/or received telephone calls. The diallog screen 725 permits access to the call details screen 760. The dialstatus screen 750 displays information about an ongoing call or calls.For one embodiment, the dial status screen 750 is automaticallydisplayed on the viewer screen whenever a voice call(s) is established.

FIG. 8A illustrates one embodiment of screen shots for a dialing processfor telephony operation. The opening screen 805 indicates that aconnection has been established with a cellular service. In oneembodiment, this screen appears when the cellular element is firstcoupled to the organizer and/or when the cellular element is initiallyturned on.

The base screen is the speed dialing screen 810. Programmed speeddialing screen 810 includes identifiers for each of the individualsprogrammed into the speed dialer. The identifiers are designated by theuser, and may be nicknames, or other identifiers. In one embodiment, thetop left hand slot is a voicemail slot. On the bottom left of the speeddialing screen 810 are indicated the other base screens, the dial padscreen 815, and the call history screen (not shown). An option to editthe speed dial listings is also provided.

At the top of the speed dialing screen 810, and every other base screenfor one embodiment, are indicators. Examples of indicator include a timeindicator, a message indicator, a signal strength indicator, and abattery strength indicator. In one embodiment, there are two messageindicators, indicating either a voicemail message or a text/e-mailmessage. In one embodiment, the message indicator may further includeservice provider information as well.

From the speed dialing screen 810, if a user presses a speed dialbutton, the screen changes to the dialing screen 820. The dialing screen820 indicates the status of the call, as well as the identity of theperson called. In one embodiment, there is a hang-up option. When thecall is connected, the call active screen 830 is displayed, showing theconnection time, and providing the options of hanging up, placing thecall on hold, placing a second call, or engaging the key pad (to dialadditional numbers, such as for a credit card call, voicemail call,dialing an extension, etc.).

If the user selects “second call”, the speed dialing screen 850 appears,although the user may optionally switch to another screen. The firstcall is automatically placed on hold. The second call is then dialed.The-two-call dial status screen 855 indicates the status of both calls.In one embodiment, only one call can be active at any time. In anotherembodiment, multiple calls may be simultaneously active, and in such acase, the calls may be conferenced together.

An alternative base screen is the dialing pad 815. The dialing pad 815displays the software generated dialing keys. When the user startsdialing, the dialing screen 825 is displayed, and the numbers dialedreplace the status indicators at the top of the screen. It is noted thatthe screen illustrated are sample screens only. Those skilled in the artwill appreciate that the location, contents, or display format of any ofdata presented on the screen can be altered or made optional withoutdeparting from the spirit of the disclosed embodiments.

FIG. 8B illustrates one embodiment of screen shots as the system isnavigated through an incoming call alert. The incoming call alertdisplays a call alert screen 865. In one embodiment, if there is acaller identification enabled, the system determines the telephonenumber of the caller. If that telephone number appears in the call list,or on any other system that indicates the identity of the caller, theincoming screen 865 is displayed, showing the telephone number andidentity of the caller. If the identity of the caller is unknown, thetelephone number is displayed as shown on screen 868. And if the calleridentification is not enabled, no identifier is displayed, as shown onscreen 870.

The user may chose to answer the call, by pushing the answer button, orignore the call. In one embodiment, the answer button may be a softwaregenerated button. In one embodiment, the user may also accept or ignorethe call by pushing a built-in button on the cellular element. If theuser ignores the call, and voicemail is enabled on the system, the callis automatically transferred to voicemail. In one embodiment, if theuser ignores the call, the call may be transferred to a user designateddestination. In addition, a missed call screen 883 is displayed, showingthe identity, telephone number, time and date of call. The user mayacknowledge the missed call, or may automatically return the call, ifcaller identification is enabled. In one embodiment, if the caller lefta message on voicemail, a third option is displayed, permitting the userto listen to the voicemail left by the caller, shown on voicemail screen886.

If the user answers the call, the active call screen 873 is shown. Fromhere, the user can place the caller on hold, hang up, dial a secondcall, or receive a second call. When a second call is received, thefirst call is placed on hold, in one embodiment. In this way, themaximum amount of information is displayed to the user, regarding thestatus of various calls and systems.

FIG. 8C illustrates one embodiment of screen shots for a call history.In one embodiment, the call history screen 890 shows availableinformation about calls made and calls received. In one embodiment, onlythe name and telephone number are displayed. In addition, the list isordered by time/date of the call. In another embodiment, the list may beordered by name. In one embodiment, the user may select details. Thedetails screen 893 shows further available information about the call.The details screen 893 shows one or more of the following: name, number,date, time, duration of call, and type of call. In one embodiment, theuser may edit the information displayed in the detail, specifically byadding/changing the name information. This would enable a user to have acomplete call history log (information).

The user can further save information from the call history. If the userselects the “save” button, a save screen 896 is displayed. This savescreen 896 permits the user to automatically add data from the historyentry to his or her speed dial list and/or address book. In oneembodiment, if other programs are supported, the user may further addthe data into other programs, such as a contact tracker, etc. In oneembodiment, the call history may interface with a contact trackingapplication, and automatically update information in the contacttracking application, as calls are made and received.

FIG. 9A is a flowchart illustrating one embodiment of adding a voicemailbox to the speed dial of the system for voicemail access. Theprocess starts at block 910. At block 915, the user selects to add a newvoicemail account to the speed dialing list. Voicemail programmed speeddial buttons are treated differently from other speed dial buttons. Atblock 920, the user is prompted to enter the telephone number and/orpassword for the voicemail account. In one embodiment, the user ispermitted to use “pause” characters or “wait for tone” characters, todial the full voicemail access code. In another embodiment, when theuser first pushes the voicemail button, the telephone number is dialed,and when the user pushes the voicemail button for a second time, thepassword is dialed. Both of these numbers are entered at this stage.

At block 925, control screen is displayed. The control screen includeseach of the commands that are generally available in a voicemail system,such as previous message, next message, back, skip message, deletemessage, forward message, back to the beginning, reply to message, etc.In one embodiment, a subset of these commands may be made available. Foranother embodiment, the user may alter this listing, and may create newcommands. At block 930, the user is prompted to enter a command orcommand sequence for each of the commands that are available in thevoicemail system. For example, in a voicemail system, pressing the “3”key may mean “delete message.”

The user can enter the number “3” underneath the command key, to programthe command. In other systems, the pressing the “7” key twice may be thecode to “delete message.” The user can enter whatever key combinationworks for the specific voicemail system. At block 935, after the userfinishes programming the voicemail system, the user is prompted to namethe speed dial button. In one embodiment, the default name is“voicemail.” However, users may have multiple voicemail accounts, andmay wish to have more descriptive names. At block 940, the process ends.The programming of the voicemail access is now complete, and the usercan access the voicemail system by pressing the speed dial button.

FIG. 9B shows one embodiment of screen shots for voicemail control. Thevoicemail button 950 is shown on speed dialing screen 955. When the userselects the voicemail button 950, the voicemail number programmed in bythe user is dialed. In one embodiment, the dialing screen is shown (seescreen 820). When the call connects the voicemail control screen 960 isdisplayed. The voicemail control screen 960 includes the controlsavailable for the voicemail system. Control screen 960 is an exemplaryscreen, showing the controls: prev(ious message), back (to the beginningof the message), pause, next (message), del(ete message), reply (tomessage), forward (message), and dial pad, for entering additionalcommands. Other layouts or sets of commands may be used. However, usingthis type of voicemail control screen 960 for all voicemail applicationssimplifies access to multiple voicemail accounts.

Additional Embodiments of A Telephone User Interface

The embodiments disclosed allow for enhanced telephony functionalityover conventional telephony systems. An embodiment of such enhancedofferings is a method and an apparatus for accessing contacts databaseand telephone services. For example, cellular telephone users often aredependent upon “speed dial” features in their cellular telephones. Atypical cellular telephone has a non-volatile memory for storing thenames and associated telephone numbers for a plurality of the user'sacquaintances. The telephone speed dial user interface then allows theuser to place a telephone call to one of the stored telephone numbersrelatively quickly and easily.

Existing mobile telephone speed dial systems can operate in a variety ofways. One such speed dial system allows the user to associate atelephone number with a unique one or two digit code. The user can thendial the number by entering the one or two digit code followed by the“SEND” key to place the speed dial call. Other systems allow a singledigit speed dial number to be dialed by pressing and holding theassociated digit key. In order for this system to be effective, the usermust memorize the codes associated with the telephone numbers.

Another existing speed dial system allows the user to utilize lettersassociated with keys on the telephone keypad to spell out the name ofthe person associated with a stored telephone number. This can be atedious process since typically three or four letters are assigned toeach button on the telephone keypad, which necessitates several keypresses for each of the letters in the name spelt. Once names have beenentered, the names may be displayed on the telephone screen. The usermay then use an input device (up/down keys or toggle switch) to scrollup and down the list to select a desired name and thereby dial theassociated telephone number. With a long list of names, it becomes verycumbersome to scroll through the list.

With the advent of more sophisticated combined handheld computer andcellular telephone systems, the telephone dialing aids can become muchbetter. The present invention introduces telephone directory methods forquickly and intuitively allowing the user of a combined handheldcomputer and cellular telephone system to locate and dial the telephonenumber of a desired. Specifically, the present invention provides atelephone application having a user interface that gives a user multipledifferent views of information that allow a user to make telephone callsin a simple intuitive manner.

The telephone user interface of the present invention comprises fourpermanently available views and a fifth view that is available whenthere is an active incoming or outgoing telephone call. The fivedifferent views consist of: a speed dial view, a dial pad view, acontacts view, a call history view, and an active call view. FIG. 10illustrates a conceptual diagram of the telephone application 1001. Asillustrated in FIG. 10, the telephone application 1001 consists of a setof principal telephone interface views 1005 that include the dial padview 1010, call history view 1020, speed dial view 1030, contacts view1040, and active call view 1050.

In a preferred embodiment, certain events will cause the telephoneapplication to automatically switch between different views. Forexample, when an incoming telephone call is detected, the telephoneapplication will automatically switch to the active call user interfaceview in order to show the user information about the incoming telephonecall.

Another event that may cause the telephone application to automaticallyswitch between different views is the entry of characters from an inputdevice such as a keyboard or digitizer pad (which can be interacted witha stylus, finger, inductive pen or other mechanism to select and inputthrough the digitizer pad). In one embodiment, the entry of analphabetic character will cause the telephone application to move to thecontacts user interface view that is used to search a database ofpersonal contact information. The contact user interface view will thenbegin to filter through the contact database using the enteredcharacter(s) as a search string. Similarly, the entry of a digit maycause the telephone application to automatically switch to the dial paduser interface view. Additional information on the various automaticuser interface view switches can be found in the sections on eachdifferent interface view.

On Screen Dial Pad User Interface

The dial pad user interface view 1010 provides a conventional dual tonemultiple frequency (DTMF) touch tone dial pad interface to users suchthat users may make outgoing telephone calls with a familiar interface.FIG. 11A illustrates one embodiment of the dial pad view. Although thedial pad user interface view is probably the most familiar telephoneapplication view to new users, the dial pad user interface view isprobably the least efficient of the various different telephoneapplication user interface views. In one embodiment, the dial pad userinterface view is set up as the initial user interface view for thetelephone application in the handheld computer and cellular telephonesystem since most users will be very familiar with the dial pad userinterface view. However, the user may later select another view for moreefficient telephone number dialing.

When a user is in the dial pad user interface view, a user can touch thetouch-tone buttons presented on the screen as illustrated in FIG. 11A todial a telephone number. Pressing the telephone icon will send theentered digits to the cellular telephone network to initiate a telephonecall. The dial pad view of FIG. 11A may be invoked even when there is anactive telephone call. In this manner, the dial pad view may be used toenter DTMF touch-tones in order to access interactive telephone responsesystem such as a voicemail system or a telephone banking system.

In one embodiment, when a user begins entering a telephone number, thetelephone number being dialed is placed in the title bar 1190. The usermay also access the last ten dialed telephone numbers by scrolling up ordown. Specifically, hitting the scroll up or down key will move throughthe last ten numbers dialed and individually display each number in thetitle bar area 1190.

In the lower left corner of the dial pad view illustrated in FIG. 11A,the user interface includes four buttons for accessing the fourpermanently available user interface views. Specifically, the buttonsinclude a speed dial view button 1110, a dial pad view button 1120, acontacts view button 1130, and a call history view button 1140. Notethat the dial pad view button 1120 is shown highlighted by invertedgraphic colors since the dial pad view is the current active view. Toselect any of the other telephone application user interface views, theuser merely selects the associated view button 1110, 1130, or 1140. Theuser may also repeatedly press an application button associated with thetelephone application to rotate through the various telephoneapplication user interface views (including the active call view ifthere is an active call).

As previously set forth, a fifth user interface view is available whenthere is an active telephone call. FIG. 11B illustrates a fifth userinterface view button known as the active call view button 1150 used toaccess an active call user interface View (that will be describedlater). Active call view button 1150 is only available when there is anactive telephone call.

If the handheld computer and cellular telephone embodiment includes akeyboard 330 as illustrated in FIG. 3A, then the user may dial atelephone number using the keyboard 330. If the keyboard contains keysthat may be interpreted as a letter or a digit, as is the case with thedial pad area 391 of the keyboard illustrated in FIG. 3C, then thekeystrokes entered from the keys in the dial pad area 391 of thekeyboard will be interpreted as numbers when in the dial pad view in thepreferred embodiment. Letter keystrokes will be ignored.

In an alternate embodiment, the dial pad user interface view is used toprovide the user with an easy means of entering telephone numbers thatuse letter mnemonics. For example, 1-800-FLOWERS is a floral servicethat uses the letter mnemonic 1-800-FLOWERS in order to have potentialcustomers easily remember the contact telephone number. However, dialinga telephone numbers with letter mnemonics can be quite difficult sincethe user must search the telephone dial pad in order to locate the DTMFkey with the desired letter. In order to allow the user to quickly entersuch telephone numbers, one embodiment allows the user to enter theletters directly and the computer will translate the letters into theproper associated DTMF tones. For example, if the text for “FLOWERS”were entered, the DTMF tones associated with dial pad numbers “3549377”would be generated. (See the alphabet to DTMF key mapping illustrated inFIGS. 11A and 11B).

Certain aliasing may occur in such an alternate embodiment. However, anintelligent program could use certain heuristics to determine the desirenumber in most circumstances. For example, if the user were to dial thefull number “1800FLOWERS” without using the option key 301 to specifythe “1800” portion as numbers, the system would not know if the firstfour digits should be numbers (“1800”) or letters that should betranslated into associated DTMF tones (“YN00” equivalent to dial padnumbers “9400”).

However, a heuristic could be used to always translate the “YN00” patterinto the common 1800 prefix for eleven digit numbers. The “FLOWERS”portion would easily be recognized as a letter mnemonic in an embodimentthat uses the keyboard of FIG. 3C since none of the letters in “FLOWERS”is on the same key as a number. However, the letter mnemonic of“LAWYERS” is ambiguous since the letter “Y” and the number “1” are onthe same key on the keyboard of FIG. 3C. In such circumstances, thesystem could use the heuristic that “All ambiguous letter/numberkeystrokes located between two certainly letter keystrokes should beinterpreted as letters”. Thus, since the “L” at the beginning of“LAWYERS” and the “S” at the end of “LAWYERS” can only be interpreted asletters, then all the keystrokes between those two letters (“AWYER”)should be interpreted as letters.

Call History View

Referring back to FIG. 10, another one of the permanently available userinterface views is the call history view 1020. The call history view1020 provides a list of previous incoming, outgoing, or missed callssuch that a user may use that information to make a new outgoing call.

FIG. 12 illustrates one embodiment of the call history user interfaceview. As illustrated in FIG. 12, the call history provides a history ofall the incoming, outgoing, and missed calls. Note that the call historyview button 1240 is now highlighted with inverted graphics. The user mayfilter the call history list may by changing the category selection 1290to select only the incoming calls, only the outgoing calls, or only themissed calls. (The “All” selection illustrated in FIG. 12 illustratesall incoming calls, outgoing calls, and missed calls.

To dial a particular number from the call history list, the user mayselect the call and then activate the dial button 1270. Alternatively,the user may simply press the space bar or return key on the keyboardillustrated in FIGS. 3A and 3C. To obtain more information on aparticular call in the call history list, the user may select aparticular call from the call history list and then activate the detailsbutton 1280.

If a user is in the call history view and begins entering alphabeticcharacters, the telephone application will automatically switch to thecontacts view. Once in the contacts view, the telephone application willbegin searching for a desired contact using the entered character(s) asa search string as will be set forth in the section on the contacts userinterface view.

Speed Dial View

Referring back to FIG. 10, another one of the permanently available userinterface views is the speed dial view 1030. The speed dial view 1030provides a list of commonly called telephone numbers for quick access.Due to its simple and intuitive design, the speed dial user interfaceview is probably the most useful user interface view of the telephoneapplication after the user has customized the speed dial user interfaceview by entering several telephone numbers into it. Thus, the user willbe encourage to make the speed dial view the initial default view aftersome speed dial entries have been created.

FIG. 13 illustrates one embodiment of the speed dial user interfaceview. In this example view, note that the speed dial view button 1310 isnow highlighted with inverted graphics since it is the current activeview. The speed dial user interface view has a title bar 1315 at the topof the screen and a command button area 1335 at the bottom of thescreen. The area 1325 between the title bar 1315 and command button area1335 on the speed dial user interface view is occupied by tenprogrammable speed dial buttons, arranged in two columns of five buttonsper column. Each of the speed dial buttons corresponds to a speed dialrecord. The speed dial record tag or label (or a portion thereof) isdisplayed on the screen button, and activating (“tapping”) a button witha label causes the telephone application to control the handheldcomputer and telephone peripheral to dial the telephone number of thecorresponding speed dial record. A user may customize all of thedifferent speed dial buttons with their own personal speed dial numbers.

The speed dial user interface view of the present embodiment implementsa page metaphor, whereby a plurality of speed dial “pages” are each usedto store a sub-set of speed dial records. In the embodiment of FIG. 13,there are five different speed dial pages. To navigate between thedifferent speed dial pages, there are a set of five numbered speed dialpage buttons 1391, 1392, 1393, 1394, and 1395 in the lower left cornerof the speed dial user interface view. The currently displayed speeddial view page is the first speed dial page such that first speed dialpage button 1391 is highlighted with inverted graphics. Tapping on anyof the other page buttons 1392, 1393, 1394, or 1395 will effect displayof the contents of that page (and that page button will then becomehighlighted).

The user may navigate though the various speed dial entries using ascroll button. In FIG. 13, the voicemail speed dial button ishighlighted with a pair of white brackets 1351, 1352. Pressing a scrolldown button would move the highlighting to the next non empty speed dialentry (“Ron Work” in this example). In one embodiment, pressing the upscroll button when the first speed dial entry is highlighted will moveto a non empty speed dial button on the next non empty page of speeddial buttons (page 2 in this example assuming page 2 has a non emptyspeed dial button). In an alternate embodiment, pressing the pressingthe up scroll button when the first speed dial entry is highlighted willmove to a non empty speed dial button on the next non empty page ofspeed dial buttons (page 5 in this example assuming page 5 has a nonempty speed dial button).

When the last non empty speed dial button of a speed dial page ishighlighted (“Greg” in this example), pressing the scroll down buttonwill move the highlight to the first non empty speed dial button of thenext non empty speed dial page (page 2 in this example assuming page 2has a non empty speed dial button.). In an alternate embodiment,pressing the scroll down button when the last non empty speed dialbutton of a speed dial page is highlighted (“Greg” in this example) willmove the highlight to the first non empty speed dial button of the samespeed dial page (“Voice Mail” in this example).

The basic operation of the telephone application from the speed dialuser interface view in ordinary operation is as follows. Each of thefive speed dial view pages has ten speed dial soft buttons that are userassignable. When a speed dial button has been assigned to a speed dialrecord by the user, that speed dial button displays the tag or label ofthe speed dial record. Tapping on (activating) a speed dial buttoncauses the automatic dialing of the corresponding assigned telephonenumber. Tapping on a speed dial button with no number assigned (e.g. anempty button) effects display of an edit speed dial page as illustratedin FIG. 15A that allows the user to generate a speed dial record to beassigned to that button.

Tapping (e.g., or otherwise selecting) on the title bar 1315 of thespeed dial user interface view reveals a pull down edit menu (notshown). Selecting the edit menu causes an edit speed dial page (1032 inFIG. 10) to be displayed. Referring back to FIG. 10, from the speed dialview 1030 the speed dial data can be entered and amended by the userthrough edit list 1032, edit entry 1034 and find number functions 1036which are described in detail hereinbelow. The layout of the edit speeddial page is illustrated in FIG. 14. The edit speed dial page providesthe primary basis by which the user can arrange speed dial settings onthe Speed Dial pages, edit speed dial records (1034 in FIG. 10) and findtelephone numbers for assignment to the speed dial buttons (1036 in FIG.10).

The Edit Speed Dial page of FIG. 14 contains a table of ten “slots”arranged in two columns of five, with each slot corresponding to a speeddial button 1125 on the speed dial user interface view. There arenotionally five edit speed dial pages, one for each of the speed dialview pages. The slots in the table contain the text of the tags orlabels for the speed dial records assigned to the corresponding buttons.When in the edit speed dial page view, one of the slots is always“selected”, and the user can change the selected slot by tapping on thecorresponding position of the table. In FIG. 14 the selected slot isindicated by inverted graphic colors.

Located below the table of speed dial buttons for a page is a set ofspeed dial page button icons 1435 that operate in a similar manner tothe speed dial page buttons 1391, 1392, 1393, 1394, and 1395 and allowthe user to navigate amongst the five edit speed dial pages. The speeddial page button icons 1435, however, are larger than the speed dialpage buttons 1391, 1392, 1393, 1394, and 1395 because they also displayan indication of the speed dial button assignments on each of the speeddial pages. This is achieved by small horizontal lines arranged in thespeed dial page button icons 1435 representing speed dial buttons onthat page that have assigned speed dial records in the specifiedlocations.

By way of example, as seen in FIG. 14, the speed dial page icon has tenhorizontal lines indicated that the first speed dial page has all slotsoccupied and thus all corresponding speed dial buttons assigned. Thesecond speed dial page icon indicates that that page has two “empty”slots/buttons at the lower right positions. Speed dial pages three,four, and five are all shown as empty in FIG. 14. This icon displayallows the user to quickly and easily determine which pages have emptyslots/buttons at a glance from the edit speed dial page view, which isparticularly useful for editing and rearranging speed dial assignmentsas described in greater detail herein below.

The edit speed dial page may also contain several command buttons at thebottom of the screen for performing specific functions. In theembodiment of FIG. 14 only a “Done” 1461 command button is illustrated.Tapping on the “Done” command button 1461 returns the user to the speeddial user interface view. Other command buttons may be implemented toenable other operations to be performed on the speed dial record of theselected slot.

Tapping on an empty speed dial slot from the edit speed dial page causesthe display of a new speed dial edit entry page as illustrated FIG. 15A.The new speed dial edit entry page displays the data of the speed dialrecord for the selected slot speed dial slot. In particular, the editentry page has a “Name” field at for displaying and editing the speeddial record tag or label, and a “Number” field at for displaying andediting the telephone number for the speed dial record.

The edit entry page also has a field labeled “Extra Digits” thatprovides the user the ability to specify a string of DTMF touch tonesthat may be sent by the user after initiating a telephone call using thetelephone number associated with the speed dial record. For example, fora particular telephone number corresponding to a voicemail system, theuser may specify a string of DTMF touch tones in the “Extra Digits”field for accessing the user's voicemail box. In another application ofthe “Extra Digits” field, the “Number” may contain a long distanceservice access telephone number and the “Extra Digits” field may specifya particular long distance account code.

The entry fields “Name”, “Number”, and “Extra Digits” in the edit entrypage are each editable by the user in conventional manner on thehandheld computer system, e.g., 300. For example, the fields can beedited using the stylus on the touch sensitive screen or using akeyboard. When editing the “Number” or “Extra Digits” fields, thecomputer system may be put into a special “number lock” mode that onlyallows numbers or other touch tone characters such as “*” and “#” to beentered. The edit entry page has several command buttons labeled “Done”1561, “Cancel” 1562, and “Lookup” 1563. Tapping on the “Done” button1561 causes the telephone application to return to the edit speed dialpage of FIG. 14, retaining any changes to the speed dial record made bythe user. The “Cancel” button 1562 effects return to the edit speed dialpage of FIG. 14 but discarding any speed dial record changes. The“Lookup” button 1563 allows the user to find a telephone number from theuser's telephone book (to be described in the next section) to insert inthe “Number” field.

Referring to FIG. 14, tapping on a filled speed dial slot from the editspeed dial page causes the display of an existing speed dial edit entrypage as illustrated FIG. 15B. The difference between the new speed dialedit entry page of FIG. 15A and the existing speed dial edit entry pageof FIG. 15B is that the existing speed dial edit entry page replaces the“Lookup” button with a “Delete” button that allows the user to deletethe speed dial record.

One special speed dial record is a voicemail speed dial recordassociated with the voicemail-box of the cellular telephone itself. Toprevent loss of this special speed dial record, the voicemail recordassociated with the voicemail-box of the cellular telephone should notbe deleteable. However, the voicemail record is moveable such that theuser can place the voicemail record into any available speed dial slot.

When a user is in the speed dial user interface view and begins enteringalphabetic characters, the telephone application will automaticallyswitch to the contacts view of the telephone application. Once in thecontacts view, the telephone application will begin searching for adesired contact using the entered character(s) as a search string aswill be set forth in the following section describing the contacts userinterface view.

FIGS. 16, 17, and 18 illustrate how the speed dial user interface viewand its associated editing views can be used to create and edit speeddial records. The editing procedures are described with reference to thepreviously described speed dial editing screens. FIG. 16 illustrates thecreation of new speed dial button beginning from an empty button from aspeed dial user interface view 1610. The user taps on an empty button1604 that opens the edit entry page 1620 used to create new speed dialrecords or edit existing speed dial records. In the edit entry page1620, the user enters data into the “Name”, “Number” and optionally“Extra Digits” fields using conventional data entry means to create anew speed dial record. Tapping on the “Done” button effects return tothe Speed Dial page 1630 with the previously empty button now assignedto the new speed dial record. The button 1605 now displays the Namefield text, in this case “Ron Home”, indicating that the speed dialbutton/slot is no longer empty.

A speed dial button insertion procedure is illustrated at in FIG. 17,beginning from a speed dial user interface page 1710. The user taps onthe title bar of the Speed dial page and selects the revealed “Edit”menu item 1704. This cause the telephone application to bring up theedit speed dial page 1720 corresponding to the speed dial user interfacepage 1710. The user selects one of the slots on the edit speed dial page1720 to edit and taps it. The telephone application then displays theedit entry page 1730, allowing the user to edit the speed dial record aspreviously described. The user taps on the “Done” button at thecompletion of the speed dial record editing to return to the edit speeddial page as shown at 1740. The selected slot now contains the editedspeed dial record. Tapping on the “Done” button effects return to thecorresponding speed dial page 1750, where the new speed dial record tagor label is displayed on the speed dial button.

A second speed dial record editing procedure is illustrated withreference to FIG. 18, beginning from a speed dial user interface view1810. The user obtains the corresponding edit speed dial page 1820through selection of the “Edit” pull-down menu item. In this case theuser selects a different speed dial page to edit by tapping on theassociated speed dial page icon 1825. An occupied speed dial slot onspeed dial edit page 1830 is selected by tapping on it to transition tothe edit entry page 1840 containing the speed dial record data for theselected speed dial slot. The user is then able to edit the speed dialrecord data as desired.

After completing the desired edits, the user taps the “Done” button tostore the amended speed dial record. The telephone application thenreturns to the edit speed dial page 1850 for the fourth speed dial page.Finally, tapping on the “Done” button on edit speed dial page 1850returns the user to the speed dial user interface view 1860 of theedited speed dial page, the fourth speed dial page in this example.

Contacts View

Referring back to FIG. 10, the final permanently available userinterface view is the contacts view 1040. The contacts user interfaceview provides the user access to a large database of contactinformation. Each contact record in the contacts database may containthe name, work address, home address, work telephone number, hometelephone number, mobile telephone number, fax number, Internet emailaddress, and other personal contact information.

FIG. 19 illustrates one embodiment of the contacts user interface view.Note that the contacts view button 1930 is now highlighted with invertedgraphics. The contacts user interface view is comprised of a title bar1915, a main area 1925, and command area 1395. As illustrated in FIG.19, the main area 1925 of the contacts view comprises an integrated listof names and associated telephone numbers. The names may be listed as“last-name, first-name” or “first-name last-name” as selected by theuser. Furthermore, the names will be displayed in alphabetical orderusing “last-name, first-, name” or “first-name, last-name” as selectedby the user. In the illustration of FIG. 19, the names are listed in the“last-name, first-name” display format and order. The names displayed inthe main area 1925 are left justified.

The telephone numbers associated with the displayed names are displayedbelow the associated name and right justified. Note that by using a fullline for the name and a full line for each associated telephone number,the display will not need to abbreviate or shorten most names ortelephone numbers. In a preferred embodiment, only the voice telephonytelephone numbers such as a home telephone number, a work telephonenumber, a main telephone number, a mobile telephone number and/or othervoice telephone number associated with each name is displayed. Faxnumbers are not displayed since it is generally not useful to dial a faxnumber from the computer-based mobile telephone system. The telephonenumbers are listed in the same order as the telephone numbers exist inthe contact record.

In the command area 1935 of the contacts user interface view resides apair of scroll buttons 1923, a “new” button 1922, and a search field1921. The new button 1922 allows the user to enter a new personalcontact record. The scroll buttons allow the user to scroll up and downthrough the list of names and telephone numbers illustrated in the mainarea 1925 of the contacts user interface view. The search field 1921allows the user to search for a particular name in the database ofpersonal contact information. In one embodiment, a search mechanism canbe used further to help manage contact in the contacts database. Thesearch system may be simple and intuitive to allow for each of use. Inone embodiment, the search field uses a multiple filter system to searchthe database of personal contact information.

The search field 1921 allows a user to enter characters from a desiredname. Characters may be entered in different manners as dependent uponthe particular handheld system. For example, the characters may beentered using a keyboard 330 or entered into a text area 125 using astylus in association with character recognition software. After eachcharacter entry, the filter system produces a filtered subset of namesand associated telephone numbers from the entire contacts database. Atleast a portion of that filtered subset is then displayed in the mainarea 1925. If an alphabetic character is entered while the user is inany of the other permanent user interface screens, the telephoneapplication will immediately open the contacts user interface view andbegin a search of the contacts database.

In a preferred embodiment, the system creates a subset that contains allnames having a first name that matches the entered letters (for example“GR” would match the name Greg Shirai), a last name that matches theentered letters (for example “GR” would match the name Bob Green), or afirst name initial and last name that matches the entered letters (forexample “GR” would match the name George Robinson).

Spaces within names are ignored for matching purposes in order to usethe space bar on a keyboard as the signal to dial the number. Thus,“vand” matches the last name of name Jean-Claude Van Damme. When a userdeletes a character, the search will add back names that now match theshorter string. Additional details on a preferred filtering embodimentcan be found in the co-pending patent application entitled“Multi-Context Iterative Directory Filter”, filed concurrently with thisapplication and hereby incorporated by reference.

Referring to FIG. 19, the user has entered the characters “CAR” in thesearch field 1921. The search letters “CAR” match the names “Harris,Carmine” and “Lamb, Carmen” since the letters “CAR” are in the firstnames of those two names. The search letters “CAR” match the names“Carter, Jimmy” and “Carnack, Mike” since the letters “CAR” are in thelast names of those two names. Finally, the search letters “CAR” matchthe names “Arnett, Candy”, “Arnold, Chevy”, and “Arnold, Clint” sincethe letters “CAR” match the initial of the first name and the first twoletters of the last name of those three names. This final filteringcriterion, the matching of a first name initial and last name is one ofthe most powerful features of the search system because there is not alarge amount of aliasing in this filter. This final filtering criteriais particular useful when searching for the contact information for aparticular family member since the common last name of family memberswill cause undesirable aliasing.

In the example of FIG. 19, if the user has family members “Arnett,Candy”, “Arnett, Kevin”, “Arnett, Paul” and “Arnett, Susan”, only thename “Arnett, Candy” is displayed since it is the only family name thatmatches the “CAR” string. At any time during a search, the user may usescroll through the currently displayed search results by using scrollbuttons 1923, scroll keys on a keyboard, or other scrolling input means.

As previously set forth, the telephone application may automaticallyopen the contacts user interface view if the user begins enteringcharacters while in the speed dial or call history view. In anembodiment that uses a keyboard containing keys that are associated withboth a letter and a digit, such as the Y/1 key on keyboard of FIG. 3C,it may be considered ambiguous as to whether the user is attempting todial a number or spell out a name.

For example, the series of keystrokes N/8, Y/1, K/6, K/6, and I/3 may bethe name “Nikki” or the number “81663”. The telephone application willassume that a name is being spelled out and search through the contactsdatabase using some filtering means. However, if there is no matchingcontact and all the entered keystrokes were from keys that have both aletter and a digit, then the telephone application will assume the useris attempting to dial a telephone number with the key pad area 391 andautomatically switch to the dial pad view and display the enteredkeystroke sequence as a series of digits. Thus, it is possible to be inthe speed dial user interface view, begin entering keystrokes,automatically switch to the contacts view, and then automatically switchto the dial pad view, if the series of keystrokes were all from the dialpad area 391 and associate letters do not match an entry in the contactsdatabase.

Referring back to FIG. 19, in the main area 1925 of the contacts userinterface view, either a name (from the left-justified names) or atelephone number (from the right justified associated telephone numbers)may be highlighted for focus. Normally, the first telephone number inthe main area 1925 is initially highlighted for focus. In FIG. 19, thename “Arnett, Candy” is highlighted with inverted graphics after a userhas scrolled upward. When a highlighted name is activated by pressing anenter key, a keyboard space bar, or other means, the system opens up afull contact editing screen for editing a contact record associated withthe selected name. When a highlighted telephone number is activated bypressing an enter key, a keyboard space bar, or other means, then thathighlighted telephone number is automatically dialed by the cellulartelephone system.

In a preferred embodiment, the telephone numbers are not displayedexactly as the telephone numbers are entered into the contact record.Instead, the telephone numbers are displayed exactly how the cellulartelephone will dial the number. Thus, any rules for adding or removingarea codes or other prefixes or postfixes should be applied beforedisplaying the number. Similarly, any extraneous text such as “ext. 123”should be removed.

In an alternate embodiment, the email address (if available) associatedwith a displayed name is also displayed. The email address may bedisplay on its own line just as the voice telephony telephone numbersare displayed. In this manner, the user of the device may highlight andactivate the email address. Activating the email address may launch anemail application with an outgoing message addressed to the selectedemail address as an initial screen display.

Active Call View

Another user interface view of the telephone application is the activecall user interface view. The active call user interface view is onlyavailable when there is an active incoming or outgoing telephone call.The contents of active call user interface screen will be dependent uponthe telephone call (incoming or outgoing) and the particular abilitiesof the carrier network. In one embodiment, the active call userinterface view will allow the user to easily access various advancedtelephone features. For example, the user may place a call on hold,initiate a three-way call, hang-up the call, enter the extra digitsassociated with an outgoing call, or turn on/off a speakerphone feature.

FIG. 20 illustrates one embodiment of an active call user interface viewfor an outgoing call to a voicemail system. To enter a DTMF account codeor password for the voicemail system, the user can select the “extradigits” button 2064 to play the extra DTMF codes entered in the “extradigits” field of the speed dial record. The user may turn on aspeakerphone feature by pressing “speakerphone” button 2063. FIG. 21illustrates another active call user interface view.

In the active call user interface view of FIG. 21, the speakerphone isactive such that the speakerphone button has been replaced with a“cancel speakerphone” button 2163. If the call was initiated using ameans other than a speed dial button associated with a speed dial recordwith a set of “extra digits” then the active call screen will provide akey pad button 2164 that can be used to access the dial pad view suchthat the user may enter DTMF touch tones. If the hardware embodimentincludes a keyboard with a dial pad area 391 as illustrated in FIG. 3C,then the user may simply enter DTMF touch tones by tapping the numberkeys in the dial pad area 391 or other keys associated with DTMF dialtones such as #, *, and +.

Telephone Application Alerts

Certain events cause special alert pages to be displayed by thetelephone application page. For example, when an incoming call isreceived, the user is presented with an incoming call alert screen.

FIG. 22 illustrates a first embodiment of an incoming call alert screenview that informs the user of an incoming call. At the top of the screendisplay 2225 is a message generated by a caller-id feature thatspecifies the telephone number 2230 of the incoming call (if available).If the incoming telephone number exists in the contact database, then alabel 2235 associated with the telephone number is displayed, in thiscase the label “Home” is displayed. The embodiment of an incoming callscreen is illustrated in FIG. 22 is delivered when the flip lid 320 ofthe integrated computer and cellular telephone system illustrated inFIG. 3A is open. The user may answer or ignore the incoming telephonecall by touching either “Answer” or “Ignore” buttons respectively.

FIG. 23 illustrates a second embodiment of an incoming call alert screenview that informs the user of an incoming call. The embodiment of anincoming call screen is illustrated in FIG. 23 is delivered when theflip lid 320 of the integrated computer and cellular telephone systemillustrated in FIG. 3A is closed. The user may answer the incomingtelephone call opening the lid 320 of the integrated computer andcellular telephone system. Similarly, the user may ignore the telephonecall (and thus stop the ringing) by tapping the upward scroll button.

If an incoming telephone call is received while the user is opening orclosing the flip lid 320 or presses a button on the integrated computerand cellular telephone system, an undesirable action may occur. Forexample, if the user is opening the flip lid 320 while an incoming callis being received, then the user may inadvertently answer the telephonecall without having a chance to review the caller-ID field. Similarly, auser may pressing the scroll up button just when an incoming call is andthe lid is closed, this might cause the integrated computer and cellulartelephone system to ignore the incoming call before the user even knewan incoming call was being received.

To prevent such undesirable effects, one embodiment of the presentinvention uses an input “lockout period”. Specifically, one embodimentignores all input events (such as lid opening event or a key pressevent) for a predefined period when an incoming call is received. Thus,if an incoming telephone call is received while a user is opening thelid, the opening of the lid will not cause the integrated computer andcellular telephone system to answer the telephone call. Instead, thesystem will display the interface of FIG. 22. Similarly, if the userpresses the upward scroll button when an incoming call is received andthe lid is closed, the button press will not ignore the telephone call.In one embodiment, the lock out period is half a second. However, it maybe adjusted to a longer or shorter period of time.

Although the detailed description contains many specifics, these shouldnot be construed as limiting the scope of the invention but merely asillustrating different examples and aspects of the invention. It shouldbe appreciated that the scope of the invention includes otherembodiments not discussed in detail above. Various other modifications,changes and variations which will be apparent to those skilled in theart may be made in the arrangement, operation and details of the methodand apparatus of the present invention disclosed herein withoutdeparting from the spirit and scope of the invention as defined in theappended claims. Therefore, the scope of the invention should bedetermined by the appended claims and their legal equivalents.Furthermore, no element, component or method step is intended to bededicated to the public regardless of whether the element, component ormethod step is explicitly recited in the claims.

1. A control mechanism for a mobile communication device, the controlmechanism comprising: a first mode element, a second mode element and athird mode element, each mode element corresponding to a distinctoperational mode associated with a particular function of the mobilecommunication device; a physical switch mechanism having a firstphysical positional state corresponding to the first mode element, asecond physical positional state corresponding to the second modeelement, and a third physical positional state corresponding to thethird mode element, the positional switch movable between each physicalpositional state to select an operational mode and to enable the modeelement corresponding to the selected operational mode.
 2. The controlmechanism of claim 1, wherein the particular function is a notificationfunction.
 3. The control mechanism of claim 2, wherein a firstoperational mode is a mute mode, a second operational mode is a soundenable mode, and a third operational mode is an actuator mode.
 4. Thecontrol mechanism of claim 3, wherein the actuator mode is configured toactuate the mobile communication device in response to its selection. 5.The control mechanism of claim 3, wherein the actuator mode isconfigured to trigger a sound in response to its selection.
 6. Thecontrol mechanism of claim 3, wherein the sound mode is configured totrigger a sound in response to its selection.
 7. The control mechanismof claim 1, wherein the particular function is a wireless networkconnection function.
 8. The control mechanism of claim 4, wherein afirst operational mode is enable GSM mode, a second operational mode isenable CDMA mode, and a third operational mode is an OFF mode.
 9. Thecontrol mechanism of claim 8, wherein each operational mode isconfigured to provide a notification through the mobile communicationdevice in response to its selection.
 10. The control mechanism of claim9, wherein the notification is a vibration pattern.
 11. A communicationsenablement physical switch for a mobile device, the switch comprising: afirst physical positional state corresponding to a first communicationmode; a second physical positional state corresponding to a secondcommunication mode, each communication mode distinct from the othercommunication mode; and a selector structured to move between eachphysical positional state and when set in a particular physicalpositional state enabling a communication mode corresponding to thatphysical positional state.
 12. The switch of claim 11, wherein the firstcommunication mode corresponds to enabling a sound playback through aspeaker of the wireless communications device and the secondcommunication mode corresponds to disabling the sound playback throughthe speaker of the mobile device and enabling a vibration mechanism inthe mobile device.
 13. The switch of claim 12, wherein a communicationmode selected through the selector is triggered in response to receiptof a communications at the mobile device.
 14. The switch of claim 11,wherein the first communication mode corresponds to placing a radio inan ON state and the second communication mode corresponds to placing theradio in an OFF state.
 15. The switch of claim 11, wherein radiocomprises one of a WiFi and WiMax radio.
 16. The switch of claim 11,wherein the first communication mode corresponds to enabling GSM networkconnection and the second communication mode corresponds to enabling aCDMA network connection.
 17. The switch of claim 11, wherein the firstcommunication mode corresponds to enabling GSM network connection andthe second communication mode corresponds to disabling the GSM networkconnection.
 18. The switch of claim 11, wherein the first communicationmode corresponds to enabling CDMA network connection and the secondcommunication mode corresponds to disabling the CDMA network connection.19. The switch of claim 11, further comprising a third physicalpositional state corresponding to a third communication mode, the thirdcommunication mode distinct from the first communication mode and thesecond communication mode.
 20. The switch of claim 19, wherein the firstcommunication mode corresponds to enabling GSM network connection, thesecond communication mode corresponds to enabling the CDMA networkconnection, and the third communication mode corresponds to disablingnetwork connections.